Skip to main content

Your data has issues

There is a problem

  • geometry column must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Organisation Felled date Entry date Start date End date
401 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
402 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
403 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
404 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
405 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
406 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
407 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
408 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
409 Mar-84 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
410 Jan-88 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
411 Dec-74 CHELSEA SQUARE

Unexpected geom type

2025-01-03
412 Dec-74 CHELSEA SQUARE

Unexpected geom type

2025-01-03
413 31/96 CHELSEA SQUARE

Unexpected geom type

2025-01-03
414 Dec-74 CHELSEA SQUARE

Unexpected geom type

2025-01-03
415 Dec-74 CHELSEA SQUARE

Unexpected geom type

2025-01-03
416 K15 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
417 K15 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
418 K15 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
419 K15 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
420 K15 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
421 May-74 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
422 May-74 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
423 Jan-87 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
424 22/89 CHEPSTOW CRESCENT

Unexpected geom type

2025-01-03
425 K27 CHEPSTOW PLACE

Unexpected geom type

2025-01-03
426 K27 CHEPSTOW PLACE

Unexpected geom type

2025-01-03
427 Jan-96 CHEPSTOW PLACE

Unexpected geom type

2025-01-03
428 See 26 Pembridge Villas CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
429 See 24 Chepstow Crescent CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
430 K15 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
431 K15 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
432 K25 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
433 K25 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
434 K25 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
435 K25 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
436 K25 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
437 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
438 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
439 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
440 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
441 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
442 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
443 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
444 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
445 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
446 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
447 K28 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
448 May-74 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
449 May-74 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03
450 May-74 CHEPSTOW VILLAS

Unexpected geom type

2025-01-03

Showing rows 401 to 450 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL